home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
netg4.zip
/
WHATSNEW.100
< prev
Wrap
Text File
|
1996-05-26
|
31KB
|
919 lines
gamma 4
-------
* The AKAFORCE statement in netmgr.cfg was broken (didn't work at all).
Problem reported by Francois Blais.
* Searching for a string (not a substring with ~) in the subject line
in an Xmask would not always work correctly.
Problem reported by Peter Karlsson.
* NetMgr's config file wasn't opened in a file sharing mode.
Problem reported by Vicki Fletcher.
* The 'PackMail' action would replace the 'subject' line in file request
messages with the name(s) of the requested file(s), even for JAM messages
with a 'real' subject line.
Problem reported by Francois Blais.
* For messages with file attaches or requests, the 'subject' line would
sometimes be empty for bounce messages. This is now fixed.
Problem reported by Pepijn Hendriks.
beta 8
------
* There were two clashes with tokens used to represent attributes.
The JAM zonegating bit is now : %
The locked status is now : $
* The variables (like %from, %to and so on) can also used in files used for
the 'AddNote' action.
* Productcode in mailpackets now set to 0xFE instead of 0x00
* The -q command line switch produced junk in the logfile.
* NetMgr would open _every_ area as a netmail area, which is not correct
when doing an EchoCopy/Move. Mails created with EchoCopy/Move could
therfore give trouble.
* When using the -@ or -# pseudo attributes, the debug output would show
incorrect information.
* Doing a copy/move on messages without any kludges resulted in a
protection violation.
* MoveMail lost names of attaches/requests from the subject line.
* Action FILE in the DOS version gave problems, that could range from not
writing the output correctly to crashing the computer.
* You can now use the variables (%from, %to etc) in Action Display. This
also fixes a problem that gamma 2 had when you specified % tokens in a
display action.
* When scanning for a certain keyword on the subject line, it was not
possible to scan for filename for attaches and requests. In areas other
than JAM, this information is actually stored in the subject line, so
scanning should be possible (but it didn't work because NetMgr stores
this information separately).
NetMgr will now also scan the list of attached/requested files when
looking for a certain string in the subject.
So doing this...
Mask Allfix, *, *, *, ~TIC, +a
Action Delete
.. should now do what it's told (delete file attach messages that come
from allfix and show the word 'TIC" in the subject, or in other words:
that have a TIC file attachd).
* Some other cosmetical things.
beta 7
------
* Don't remember what happened here :-)
beta 6
------
* The 'dest' keyword in XMASKs didn't work (at all).
* NetMgr stripped the already existing trailing VIA lines when packing mail
(it just added it's own :-)
* NetMgr now also allows the OR construction for attributes. So something
like this is now also possible:
XMASK
From Gerard van Essen
Orig 2:281/527.0
Attr +c OR +a+l OR +f-c
END
This mask will match for messages that are flavoured crash, or are
flavoured 'attach' and 'local', or flavoured 'request' but NOT crash.
Please note that this construction is not valid for the attributes that
need to search the nodelist (# and @). You can specify these attributes
like this, but they are checked once, separately from the other
attributes.
So you cannot specify:
Attr +c-@ OR -c+@
or something similar. You can only specify these attributes once and they
will then be carried over to all other attribute masks. In other words,
specifying this:
Attr +c-@ OR +l
will actually be expanded to:
Attr +c-@ OR +l-@
beta 5
------
* Added the ability to run external programs from NetMgr.
The action to use for this is RUNEXTERNAL.
Format:
RUNEXTERNAL <program to use> <parameters>.
In the <paramaters> part, you can make use of several 'variables', whose
value depends on the contents of the header of the message that triggered
the action. The following variables are available:
from - Name in the 'from' field of current message.
to - 'to'
subject - 'subject'
orig - Origination address of current message (like 2:281/527).
dest - Destination address of current message (like 2:281/527).
areadir - Directory or base name of current area, board number if
Hudson. This is in the format that is also used in
NetMgr.cfg, so $<path+basename> for a Squish area,
!<path+basename> for a JAM area etc.
msgno - Message number of current message ('relative' number for
Squish and Hudson)
realmsgno - Real message number, for Squish (UMSGID) and Hudson (real
number in Hudson base, not the relative number in the area).
For JAM and *.MSG, this is always equal to msgno.
file - Name of the file that contains the body of the message.
newfile - Name of a new file to create if you want to replace the body
of the message with new text.
repfile - Name of the file that should be created if you want to send
a message back to the sender of the message. (See below).
attach - Files attached to this message (list of files).
request - Files requested in this message (list of files [!passwords]).
(But then on one line, evidently).
Before running the external program, NetMgr will write the body of the
message to a file. This file (and other files) will be created in the
directory where NetMgr found it's config file. The path+name of this file
is available through the variable [file]. It will be:
"<path to config file>\netmsg.msg".
NetMgr will then run the external program, and check for the existence of
two files:
■ "<path to config file>\netmsg.new" : if this file exists, NetMgr will
replace the body of the message with the contents of this file. The
path+name of this variable is available through the variable
[newfile].
■ "<path to config file>\netmsg.rep": if this file exists, NetMgr will
send a message back to the sender of the message that triggered this
action.
What is actually done, is an XEMPTYBOUNCE action. For this action, the
netmsg.rep file is used as the body (where the variables like [from],
[to] etc. can be used), but where the first line of this .rep file is
used as the 'mask' for the reply header.
Because it actually _is_ an XEMPTYBOUNCE, it also follows the same
conventions as the XEMPTYBOUNCE action, so it initializes the fields
with a standard reply header, which makes it possible to use a simple
'*, *, *, *, *, *' mask (see XEMPTYBOUNCE action for more info).
The path+name of this variable is available through the variable
[repfile].
An example:
Action RUNEXTERNAL pgp.exe +batchmode -sta -u art -o [newfile] -z pass [file]
could expand to:
'pgp.exe +batchmode -sta -u art -o c:\net\netmsg.new -z pass
c:\netmgr\net.msg'
This would run PGP on the message, and sign the text. The body of the
message will be replaced with a signed version of the text.
An example of usage of a .rep file could be:
Action RUNEXTERNAL reply.cmd [repfile]
And the contents of 'reply.cmd' could be:
@echo off
echo Automatic Reply, @myaka, *, *, Response to your message, * >> %1
echo Hello %%ffrom! >> %1
echo. >> %1
echo This is an automatic reply! >> %1
echo. >> %1
echo Greetings! >> %1
This would create a netmsg.rep file, and NetMgr would send back a small
message to the sender of the original message.
* Several actions have a similar counterpart, that can place the resulting
message in another area.
The actions concerned are: the Bounce and XBounce 'family', Forward and
MakeMsg. In order to place the resulti